fix: improve bridge message when agent socket is not found#157
Merged
benvinegar merged 1 commit intomainfrom Feb 24, 2026
Merged
fix: improve bridge message when agent socket is not found#157benvinegar merged 1 commit intomainfrom
benvinegar merged 1 commit intomainfrom
Conversation
Replace the misleading 'Agent is starting up' message with a more actionable one that tells the user the agent is not connected and suggests running 'sudo baudbot restart' to fix it. The old message assumed the agent was booting, but the common cause is a stale session UUID or a crashed agent process.
Greptile SummaryImproved the error message shown to users when the Slack bridge cannot find the agent's socket. Changed from misleading "Agent is starting up" to a more accurate message indicating the agent may be disconnected, restarting, or the session expired, with actionable recovery instructions ( Confidence Score: 5/5
Important Files Changed
Last reviewed commit: 8bc0e66 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| if (!currentSocket) { | ||
| logError("🔌 no pi socket found — agent may not be running"); | ||
| await say(event.channel, "⏳ Agent is starting up — try again in a moment.", event.ts); | ||
| await say(event.channel, "🔌 Agent is not connected — it may be restarting or the session expired. Run `sudo baudbot restart` to bring it back.", event.ts); |
There was a problem hiding this comment.
The legacy bridge in bridge.mjs:268 still has the old "Agent is starting up" message. Consider updating it to match this improved message for consistency.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Prompt To Fix With AI
This is a comment left during a code review.
Path: slack-bridge/broker-bridge.mjs
Line: 702
Comment:
The legacy bridge in `bridge.mjs:268` still has the old "Agent is starting up" message. Consider updating it to match this improved message for consistency.
<sub>Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!</sub>
How can I resolve this? If you propose a fix, please make it concise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When the bridge can't find the agent's pi socket, it tells the user "Agent is starting up — try again in a moment." This is misleading — the usual cause is a stale session UUID or a crashed agent, not a slow startup.
Fix
Replace with a more accurate and actionable message:
Testing
All 15 test suites pass (
bin/test.sh).